🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18737

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (3 Unrelated Failures)

As of commit 651e4f4 with merge base 107eb92 ():

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@SS-JIA has exported this pull request. If you are a Meta employee, you can view the originating Diff in D99707657.

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@robert-kalmar There are efforts within Meta to upgrade to new numpy versions; it seems that some changes in the NXP backend will be needed for this. Just want to check with you guys if the changes make sense.

@robert-kalmar There are efforts within Meta to upgrade to new numpy versions; it seems that some changes in the NXP backend will be needed for this. Just want to check with you guys if the changes make sense.

@SS-JIA, understand. The changes are legit. It is only Meta internal upgrade, or OSS ExecuTorch too? This PR contains just the update for the API used to NUMPY, but not the numpy version - https://github.com/pytorch/executorch/blob/main/pyproject.toml . Is the intention is allow both numpy 2.x and 3x or the update is just split into multiple PRs?

FYI, such a PR was already opened by @rascani #16714 some time ago, but not merged.